Summary

Adds UrlParams marker interface to put on record classes that should be injected into an endpoint method. Any @Validation constraint in the record will be validated before mapping the request parameters to the record. In case of validation errors a BadRequestException is thrown (as it should be a "user error").

To test the concept I applied it to 2 cases, MinMaxDataElementParams and DataValueChangelogQueryParams.

Automated Testing

Existing tests got adjusted (mostly the test setup that was affected by the slightly different way of constructing params).
A new test was added for the URL parameter to JSON mapping.
As most of the actual implementation is within json-tree the relevent code is covered with many unit-tests in the library.

Manual Testing

• test /api/minMaxDataElements?page=2&pageSize=5&fields=min&fields=source and vary URL parameters
• test /api/audits/dataValue?page=2&fields=dataElement and vary URL parameters (in particular using values that should be rejected)

Documentation

• Presentation: https://github.com/dhis2/dhis2-core/wiki/Formal-Validation-with-@Validation
• JURL: https://github.com/dhis2/json-tree/blob/main/JURL.md
• Validations: https://github.com/dhis2/json-tree/wiki/Validation